Proposed by Benjamin Van Ryseghem (profile, biography)
How will I do that project
I will do this project test oriented. Even if it can be tricky to write unit tests for UI, I would like at least to have some proof of concept for multiple framework (maybe seaside, maybe cocoa) to be able to measure later the impact of changes.
What methodologies will I use
I like to have weekly meetings with my mentor to be able to have quick and fast feedback. This way the impact of the mentor can be real, and his validation is done along the process.
I am also a fond of the pomodoro technique because it allows to be very efficient, but also because it keep a highly precise track of what have been done.
Suggested timeline and milestones
Over three months, I would like to be able to run a spec tool written for Morphic on another framework within one month and a half. Then spending the other month and a half to write different bridges, and see how to make spec dialect independent.
Where I see the risks
I think that the main infrastructure for supporting independency is here, but still need to be polished. Also, learning different back end frameworks could be tedious (depending of the complexity of the framework)
How the results will look like
The result will be a Spec application written and running in Morphic being able to run also on Seaside and on Cocoa (by example), without having to change a single line of code :)
|